Add note concerning startyear/endyear to get_pvgis_tmy #1362
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
get_pvgis_tmy
results don't match PVGIS website #1360- [ ] Tests added- [ ] Updates entries todocs/sphinx/source/api.rst
for API changes.- [ ] Adds description and name entries in the appropriate "what's new" file indocs/sphinx/source/whatsnew
for all changes. Includes link to the GitHub Issue with:issue:`num`
or this Pull Request with:pull:`num`
. Includes contributor name and/or GitHub username (link with:ghuser:`user`
).The
get_pvgis_tmy
function defaults to using all available years to generate the TMY, whereas the PVGIS website only allows for 10 years to be used. I propose to add a note explaining this difference to eliminate any confusion of why the results sometimes differ, e.g., #1360.Also, I changed a number of single-backticks to double-backticks as per the recommended convention.